Providing toll free data in a wireless system

ABSTRACT

A wireless data-oriented service provides toll free data access to wireless users, such as GSM or CDMA-based users, when accessing specified content. The content provider pays for (“sponsors”) access to specific content for wireless users, often in conjunction with advertisement campaigns. In one embodiment a separate access point name is used when making the request to distinguish between sponsored data and conventional data access requests. In another embodiment, a portal proxy is used and sponsored data is distinguished from conventional data by the address of the destination web site. Wireless users accessing the sponsored content are not billed for usage, but rather the content provider is billed for usage. A data session management platform generates appropriate call data records indicating the session usage and transmits the records to reconcile accounts between the mobile network operator and the content provider.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/970,152, filed Dec. 16, 2010, the contents of which are herebyincorporated herein in its entirety by reference.

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention generally pertains to providing wireless access toa server by a mobile user wherein data charges associated with accessingthe server are borne by the content provider.

2. Prior Art

The GSM system for mobile communications includes the capability ofestablishing not only voice traffic, but data traffic. This capability,called Generalized Packet Radio Service (“GPRS”) is used to transferdata, including Internet Protocol (“IP”) structured data. The datacommunication capability is increasingly popular with the growth ofso-called “smart phones” and other wireless devices, such as tablets,that are capable of displaying text, images and rich media. Commondata-oriented applications include mobile web browsing, accessinglocation based maps, sending photos, responding to email, Voice over IP(“VoIP”), etc. Thus, many of the common data applications used by GSMusers rely on GPRS for data transfer.

Typically, GSM service providers charge a separate fee to subscribersfor data service. Two common data plans are offered by wireless serviceproviders. A minority of users have “unlimited” data plans where themonthly fees for sending/receiving data are fixed regardless of datausage. These so-called “unlimited data plans” allow transferring anunlimited amount of data to/from a mobile station each month. The othercommon data plan is called a “tiered,” “measured service,” or “metered”plan.” In a tiered plan, subscribers have a tiered data pricing plan,where limited amounts of data (usually measured in megabytes) can betransferred for a fixed fee each month. Typically, there are differenttiers or levels of fixed fees reflecting different levels of datatransfer. Data transfer during a billing period that exceeds a limit fora given tier is then billed at the higher tier. Thus, fees increase asusage increases.

In addition to the above unlimited and metered plans, wireless users maypay for wireless data transfer service on a post-paid or pre-paid basis.A post-paid arrangement is where an invoice is sent to the userindicating an amount due for services already rendered. A pre-paidarrangement is where data usage is paid for in advance of receivingservices. User's pay in advance for data usage, and their availablecredit may be decremented as data services are consumed. These can bepre-paid tiered plans, or pre-paid unlimited plans. Other variations arepossible. For example, unlimited usage plans may be defined for a dailybasis, billing period basis, or some other term.

A prepaid or tiered data service plan can serve as an incentive for auser to limit their data usage. Content providers are thus indirectlycompeting for users' access when the user has a limited data plan.Because users may not readily know how much data has been transferredrelative to the allotted amount, users may be hesitant to use any dataafter a time period into their billing cycle. Thus, incidental orspontaneous mobile browsing may be limited by a subscriber's fear ofexceeding their monthly tiered data plan and having to pay additionalfees. One solution to avoid this disincentive is to provide a mechanismfor the content provider to pay for data usage in certain cases. Inessence, any data transferred by a user when accessing, for example, aspecified web site, would not be considered as part of the user'smonthly data volume.

This application is not unlike the development of toll-free telephoneservice (a.k.a. “800 service”), which was developed to encourage use ofthe telephone for long distance calls. At that time, phone usage wasfrequently billed on a measured service basis—e.g., long distance callswere charged based on time and distance. Callers were hesitant to usethe phone to place orders or receive product information from businessesthat were not local because long distance calls incurred additionalfees. The provision of toll free telephone service encouraged people touse their telephone to call distant businesses without fear of incurringlong-distance charges.

Similarly, toll free data access for mobile users can be used bybusinesses to encourage access to their respective business web sitesand thus drive customer traffic to their web sites for reviewingproducts, placing orders, etc.

Thus, systems and methods are required for facilitating toll free datausage for mobile users.

BRIEF SUMMARY OF THE INVENTION

One embodiment of the invention comprises a method for providingsponsored data to a wireless user comprising the steps of receiving arequest at a Data Session Management Platform (“DSMP”) at an interfaceto a mobile network operator serving said wireless user, wherein saidrequest is for sponsored data from a server operated by a contentprovider, said request comprising an identification of said sponsoreddata in said server, determining from said request by a processor insaid DSMP a sponsored data campaign end date, determining by saidprocessor that said sponsored data campaign end date has not occurred,generating a second request by said DSMP to said server for saidsponsored data, receiving said sponsored data from said server at theDSMP, providing said sponsored data to said wireless user by the DSMP,and generating in said DSMP a usage record for charging said contentprovider for said sponsored data transfer.

In another embodiment of the invention comprises a system for providingsponsored data to a wireless user comprising a Data Session ManagementPlatform (“DSMP”) comprising a processor configured to: receive arequest for toll free data transfer from a Gateway GPRS Support Node(“GGSN”) of a mobile network operator serving said wireless user, saidrequest identifying a server offering said sponsored data, determinefrom said request a toll free campaign data parameter comprising a tollfree campaign end date, determine said toll free campaign end date hasnot yet occurred, generate a second request to said server for saidsponsored data, receiving said sponsored data from said server at theDSMP, providing said sponsored data to said wireless user by the DSMP,and generating in said DSMP a usage record for charging said contentprovider for said sponsored data transfer, wherein said system furthercomprises a first interface for receiving said request at said DSMP froma GPRS support node (“GSN”).

The above embodiments are only two of the various embodiments describedherein, and are not intended to limit the scope of the claims herein.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 illustrates one prior art approach of conventional data billingin one wireless environment;

FIG. 2 illustrates one embodiment of providing sponsored data;

FIG. 3 illustrates further details for one architectural embodiment forproviding sponsored data;

FIG. 4 illustrates one architecture embodiment for providing sponsoreddata in a GSM environment using multiple access point names;

FIG. 5 illustrates one messaging diagram for providing sponsored data ina GSM environment using multiple access point names;

FIG. 6 illustrates one embodiment of providing sponsored data using aportal proxy approach;

FIG. 7 illustrates one processing flow for providing sponsored datafinancial settlement reports using multiple access point names;

FIG. 8 illustrates another processing flow for providing sponsored datafinancial settlement reports using a portal proxy approach; and

FIG. 9 illustrates one embodiment of a data session management platform.

DETAILED DESCRIPTION OF THE INVENTION

The present invention now will be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments of the inventions are shown. Indeed, these inventions may beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense.

Although certain methods, apparatus, systems, and articles ofmanufacture have been described herein, the scope of coverage of thispatent is not limited thereto. To the contrary, various embodimentsencompass various apparatus, systems, and articles of manufacture fairlyfalling within the scope of the appended claims either literally orunder the doctrine of equivalents.

As should be appreciated, the embodiments may be implemented in variousways, including as methods, apparatus, systems, or computer programproducts. Accordingly, the embodiments may take the form of an entirelyhardware embodiment or an embodiment in which computing hardware, suchas a processor or other special purpose devices, is programmed toperform certain steps. Furthermore, the various implementations may takethe form of a computer program product comprising a computer-readablestorage medium having computer-readable program instructions embodied inthe storage medium. Any suitable computer-readable storage medium may beutilized including, but not limited to: technology based on hard disks,CD-ROMs, optical storage devices, solid state storage or magneticstorage devices.

The embodiments are described below with reference to block diagrams andflowchart illustrations of methods performed using computer hardware,apparatus, systems, and computer-readable program products. It should beunderstood that the block diagrams and flowchart illustrations,respectively, may be implemented in part by a processor executingcomputer-readable program instructions, e.g., as logical steps oroperations executing on a processor in a computing system or othercomputing hardware components. These computer-readable programinstructions are loaded onto a computer, such as a special purposecomputer or other programmable data processing apparatus, to produce aspecifically-configured machine, such that the instructions whichexecute on the computer or other programmable data processing apparatusimplement the functions specified in the flowchart block or blocks.

The present invention is described herein using a GSM-based wirelessarchitecture. However, the principles of the present invention are notlimited to being used only in a GSM based wireless system, and hence canbe applied to other wireless architectures, including spread-spectrumbased, 4G based, UMTS, 1x/EvDO, Wi-Fi, or other wireless architecturesand/or protocols. Certain embodiments may involve a combination ofwireline and wireless communication. Further, the inventive concepts arenot limited to wireless communication networks, but can apply towireline embodiments, including cable, fiber and DSL based distributiontechnologies. The benefits of the present invention extend, and can beapplied to, wireless or wireline subscribers that are on a metered orprepaid payment data plan.

Service Overview Background of Rate Plans

GSM based wireless subscribers are typically charged a separate fee foraccessing data services. In this context, data services encompass GSMPacketized Radio Services (“GPRS”) based services. GPRS servicestypically encompass common wireless data services involving a smartphone, such as mobile web-browsing, transmission of email (sending orreceiving), downloading data from a website, etc. In one common pricingstructure, subscribers may pay a fixed fee for an unlimited amount ofdata transfer. Thus, the “unlimited” data transfer plan does not requiremeasurement of data usage for purposes of billing the subscriber.However, a service provider may opt to measure data usage neverthelessfor other reasons. Even if the user is not capped at a limit, orotherwise billed according to how much data is transferred in a billingperiod, there remains a need by the service provider to determine thatthe subscriber is authorized to use the various data services.Obviously, not all wireless users subscribe to a data plan, and attemptsby such users to access a data service should result in a denial of theservice.

In another pricing plan (a.k.a. “rate plan” or “pricing structure”), thesubscriber is charged a fee for a defined level of data transfer. Anydata transfer beyond that level in the billing period may be charged ata different (usually higher) level. This plan allows an expected levelof data usage to be provided for a fixed fee, but usage above the levelmay be charged at the higher tier, or can be charged on a per-unitbasis. This type of rating plan is referred to herein as a “capped” dataplan. Other pricing structures and variations can be defined. It is notrelevant for illustration of the principles of the present invention todefine each of the possible tiered pricing structures, as this is simplyto illustrate a motivation for providing toll free data access.

In the unlimited data rate plan, the subscriber is not motivated tolimit their data usage based on tiered pricing. The subscriber ischarged the same fixed fee regardless of the amount of data transferredor consumed. However, some service providers are finding that unlimiteddata plans are becoming less profitable. This is because, in part,because subscribers may be downloading videos that involve large amountsof data transfer, and which require significant network resources. Thus,some service providers are migrating away from offering unlimited dataplans and directing subscribers towards capped or tiered data plans.Further, in many cases, subscribers opt for capped data plans becauseusually these are lower in cost if small amounts of data transfer occurduring a billing interval. For subscribers with capped data plans, theyare often sensitive to data usage, because the fees incurred when theyexceed the cap can be expensive.

One service architecture in the prior art for providing GPRS dataservice and billing the user is shown in FIG. 1. In FIG. 1, the mobileuser represented by a mobile station set 100 makes several data-orientedservice requests 101 over time. These requests may involve accessingcontent from various content providers 106 a-c. The requests arereceived by the GPRS System 102, which is interconnected to the Internet104, which transmits and receives data 103, 105, 107, involvingdifferent content providers 106 a-c. In this example, a total of X+Y+Zmegabytes (“MB”) of data are transferred at different times involvingdifferent content providers. The GPRS System 102 reports the amount ofdata transferred to a Billing System 108, which processes theinformation in accordance with the rate plan in place for thatsubscriber. The billing system communicates an invoice 120 (typically aprinted bill that is mailed or an electronic bill that is emailed to thesubscriber). In response, the subscriber returns payment 121 of therequested amount, which is processed by a service representative 114 toupdate the subscriber's account.

This is a simplified representation of the prior art, which does nottake into account roaming and other variations, but is sufficient toillustrate how the present invention improves upon the prior art.

Sponsored Data Overview

“Sponsored data” or “toll free data” is the name of the servicedescribed herein, wherein the wireless user is not charged for certaintypes of data usage. The content is referred to herein as “toll freedata” or “sponsored data.” The source of the sponsored data, which istypically provided via accessing a web site, is referred to as the“sponsored data content provider” or simply “sponsored contentprovider.” Other variations based on this terminology may be used.

In certain embodiments, the toll free data usage could be based onaccessing data from the sponsored content provider during a certain timeperiod or time window. In other embodiments, the toll free data pertainsto transferring a certain amount of data (e.g., such as data associatedwith a video). For example, a wireless user could have data chargeswaived for accessing a given web site for the next 10 minutes afterreceiving notification, or for 10 minutes after initially accessing theweb site. The distinction between these two examples simply involveswhen the time period begins. Another approach, may allow the user toview all the data provided by the web site for that particular sessionor subject matter. For example, an automobile manufacturer may sponsorstreaming a 5 minute video comprising a commercial regarding thefeatures of their car. The viewing of this particular video, or othervideos pertaining to that particular automobile model, may occur on atoll free basis. In each of these embodiments, the user establishes asession with the content provider. This is also sometimes referred to asa “sponsored data session” or simply a “sponsored session.”

The sponsored data can be various forms of hypertext transfer protocol(“HTTP”) formatted data provided from a web site to a mobile device.However, the sponsored data is not limited to HTTP formatted data, andcan include other formats or protocols. Specifically, the data cancomprises voice, visual or video oriented data (specifically includingdigitized voice, JPEG, or various MPEG or similar formats). Further, therequested data does not have to be requested from a web site by abrowser in a mobile device, but could be obtained from a server by anapplication running on a mobile device. The principles of the presentinvention are largely illustrated herein as obtaining HTTP formatteddata from a web site using a mobile browser, but this is for purposes ofillustration and not for limiting of the scope of the invention.

The sponsored data sessions can be initiated in a number of ways. In oneembodiment, an SMS (instant message) is sent to a user's phone alertingthem of an opportunity to access toll free or sponsored data. This canbe sent out by the content provider, an advertiser, mobile networkoperator, or some other party. The SMS message will typically indicate alink that can be accessed by the user on a toll free basis. For example,a message sent to a user could be: “To receive a video commercial aboutthis new product without charge, please select the following link.”

In another embodiment, the content provider can include information inan advertisement for accessing a toll free data website. Theadvertisement could be any of the conventional forms, as well aselectronic in form. Access to toll free data could be indicated via anicon associated with the ad. In one embodiment, the ad is visuallyoriented (e.g., a print ad), and the advertisement includes a bar-codeindicated thereon. The user could use a mobile application on theirmobile phone to capture an image of the bar-code, process the bar codeinformation to identify a web site, and access the appropriate web site.Such mobile applications can be downloaded to a mobile phone orincorporated into the phone at time of manufacture.

Another embodiment involves using Near Field Communication (“NFC”)techniques that can be based on limited range wireless communicationtechnology, such as Blu-Tooth®, infrared, or RFID based technologies.The presence of the mobile phone near a particular product could bedetermined by a NFC technique, and used to trigger sending informationto the wireless user indicating the ability to access sponsored data. Ofcourse, the wireless user could also use a browser or other applicationdownloaded to the mobile phone for accessing a sponsored web site. Thus,in one embodiment, the wireless user may be physically located near aproduct which “advertises” its presence. Upon taking action to accessthe sponsored data, the wireless user has the ability to obtain furtherinformation about the product on a toll free data access basis.

The user may receive as part of the notification, or when initiallyaccessing data from a web site, information indicating that the datarequested is sponsored data and that no charge will be incurred foraccessing the data. An indication may be provided to the user regardinglimitations in accessing the data, such as the toll free aspect isavailable for a specified time window, time duration, or for an amountof data that is accessed. The content provider may provide anotification or warning indication when the user is about to exceed theterms of use, or is about to be charged for further usage. For example,information on the web site could indicate that the time period for tollfree access is about to expire, or that the usage levels for sponsoreddata are about to be exceeded. The notification could inform the userthat continued use will be billed at the subscriber's regular rate.Similarly, if the user requests to leave the sponsored data contentprovider (e.g., to access another web site), an indication may beprovided to the user indicating that toll free data access will nolonger be provided.

Campaign Management

Provisioning of sponsored data is typically associated with anadvertisement campaign. Similarly, sponsored data is associated with itsown sponsored data campaign (or simply a “campaign”). Unless statedotherwise, “campaign” refers to the sponsored data campaign, while“advertisement campaign” refers to promotion of goods and/or services.Typically, the advertising campaign and sponsored data campaign arecoordinated. A sponsored data campaign broadly refers to the set ofinformation required to provide toll free data. In addition, the sponsorwill typically contract with a third party, where the third partyarranges (or otherwise is responsible for ensuring) that the data usagefees associated with the sponsored data transfer are waived orsuppressed. The third party could be an advertiser, a wireless serviceprovider, or an entity providing wireless data billing services to thewireless service provider. Ultimately, the third party must coordinatewith the entity providing wireless billing processing for the wirelessnetwork operator. For example, the third party could coordinate thecontent provider with the mobile network provider to ensure thatsponsored data is provided for the duration of an advertisementcampaign. In some embodiments, the third party is the same entity thatprovides bill processing for the mobile network operator or the mobilenetwork operator itself.

An advertising campaign typically has a duration, e.g., a starting dateand an ending date. Similarly, a sponsored data campaign is alsoassociated with a time period during which toll free data is provided.The area of service where toll free data may be accessed may be limitedas well. Thus, coordination between the content provider and billingprocessor of the mobile network operator is desirable.

The campaign for providing toll free data typically requires the contentprovider to pay for (e.g., “sponsor”) the data transfer on behalf of thewireless user. Hence, the content provider may also be referred to asthe “sponsor.” The content provider is often the same entity as the tollfree sponsor, but in many cases the entity coordinating and arrangingthe provision of toll free data at a high level may not be the sameentity actually providing the content (sponsored data) at an operationallevel. For purposes herein, the content provider and the sponsor areconsidered to be the same, but it is noted that these can be separate.The sponsor may contract with a third party to actually generate theinformation, load it into a server, and operate the server. Thus, thecontent sponsor will typically agree to a pricing structure associatedwith providing the sponsored data. This can be based on a flat fee persubscriber accessing the content, a rate for per time period of use($0.10 per minute of use), a rate for the amount of data transferred, orsome other arrangement. In addition, the content provider could bebilled for establishment of the campaign, providing reports of usage,reconciliation of payments, etc.

Toll Free Data Architecture

FIG. 2 illustrates one architecture of an embodiment of the presentinvention, which for purposes of illustration focuses on an embodimentbased on GSM wireless service. In FIG. 2, the mobile station set 100 caninitiate various service requests at different or simultaneous timesresulting in transferring a total of (X+Y+Z) megabytes of data. In thisembodiment, all data passes through the GPRS system 102 and sponsoreddata will also pass through the Data Session Management Platform(“DSMP”), so that the total sponsored data transferred and/or theduration of a sponsored data session is readily ascertainable by theDSMP. As it will be seen, in other embodiments, the non-sponsored datamay bypass the DSMP (or transparently pass through the DSMP). In thisembodiment, the GPRS forwards the data to DSMP 200, which in turn isconnected to the Internet 104. The requests and associated data sessionsfrom the user are shown as going to three content providers 106 a-cthrough the DSMP, with each content provider respectively providing X,Y, and Z megabytes of data. In this embodiment, content providers 106 aand 106 b each are referred to as “sponsored content providers,” orsimilar such terms. Content provider Z is a conventional contentprovider—e.g., data transferred from content provider Z is billed at thesubscriber's prevailing rate plan. In contrast, sponsored data that thesponsored content providers provide is exempt, so-to-speak, fromimpacting the subscriber's data usage. Specifically, the serviceprovider does not bill the subscriber for the sponsored data transfer,and thus, the amount of sponsored data is not used in computing thebillable data used by the subscriber.

The DSMP tracks data usage associated with sponsored content provider106 a and 106 b for each wireless user or session. It typically alsomanages campaign data, such as the beginning and ending dates of thecampaign with respect to user requests, facilitates billing, may manageaccess control based on various parameters to the content provider, andin some embodiments, the DSMP may employ a proxy server function. In theembodiment in FIG. 2, the DSMP receives all sponsored data and thus isable to readily ascertain sponsored data usage. The DSMP 200 thencoordinates (or otherwise facilitates or arranges) payment for thesponsored data usage incurred for the subscriber. The DSMP 200 mayinform 210 the billing system 108 of the mobile network operator as wellas the account payable system 107 of the sponsored content provider asappropriate. This can be done in real time, on a monthly basis, oraccording to some other schedule. The information includes the metricsused to measure the sponsored data (e.g., time, data transferred, etc.).Thus, both the content provider (who is paying for the sponsored data)and the mobile network operator (who is receiving the payment) are madeaware of the respective sponsored data usage, and thus the correspondingfinancial amount, involved for the sponsored data service. Theinformation typically includes at least an identifier of the subscriberin some form, when the data was transferred, and the amount of datainvolved. In other embodiments, aggregate data can be provided on aperiodic basis. Other indications, such as currency involved, settlementdate, etc. can be indicated.

One skilled in the art will recognize that the functionality performedby the DSMP can be integrated with the GPRS (specifically, the GGSN, asit will be seen). Other configurations are possible, includingincorporating all or some of the functionality of the DSMP in thebilling system. For example, in FIG. 2, all the data is shown as passingthrough the DSMP 200. In other embodiments, (see, e.g., FIG. 3), thenon-sponsored data does not pass through the DSMP.

The function of ensuring that the subscriber's invoice does not reflectsponsored data usage can be viewed as a separate function fromprocessing data for billing the content provider for the respectivesponsored data usage. However, these functions are typically performedin a coordinated manner. Specifically, ensuring that the subscriber doesnot pay for sponsored data usage is typically associated with ensuringthat the mobile network operator is compensated by the sponsored contentprovider. In one embodiment, the amount of the reduction in the invoiceto a subscriber could be equal to the amount charged and received fromthe sponsored data content provider. In other embodiments, the contentprovider may be providing sponsored data at a wholesale rate, so thatthe per-usage rate is lower compared to the subscriber's usage rate.

Typically, the content provider will be paying for numerous sessionsinitiated by a number of wireless users during a campaign period. Hence,a rating arrangement for the content provider is likely to reflect adiscount for larger data usage. In one embodiment, the content provideris billed at a rate that is independent of the subscriber's rate plan.The content provider may be billed a flat fee per user session attempt,tiered usage rates based on volume, a fixed fee for the campaign, etc.Other variations for rating the sponsored data usage can be developed byone skilled in the art. The sponsored content provided can be billedonce during a campaign, or periodically during a campaign.

The function of processing data usage for the purpose of invoicing thesponsored content provider and/or arranging compensation to the mobilenetwork operator is illustrated in FIG. 3. In this embodiment, the GPRSinfrastructure 102 is shown as comprising a base station 302 which isconnected to a Serving GPRS Support Node (“SGSN”) and a Gateway GPRSSupport Node (“GGSN”). The SGSN authenticates the mobile station,performs the mobility management, maintains registration information ofmobile stations and routes data packets to the correct GGSN forsubsequent access to the external interface. The SGSN also performscharging functions. Specifically, the SGSN itself does not render aninvoice or bill the subscriber, but obtains information which is used asthe basis for charging the subscriber. The GGSN acts as an interface anda router to external networks, such as the Internet, and also collectsusage information associated with the use of external data transfer.

In one embodiment, which is shown in FIG. 3, the GGSN determines whethera user request is associated with sponsored data or a conventional data,and may route the information accordingly. For example, in FIG. 3, theGGSN 308 may route conventional (e.g., non-sponsored) data over facility321 to the Internet 104, which connects to a conventional contentprovider 119. However, if the request is for sponsored data, the GGSN308 may route the data to the DSMP, which then routes the data overfacility 323 a through the Internet 104, over facility 323 b to thesponsored data web site 327.

The DSMP 312 collects information regarding how much data wastransmitted and received from a sponsored content provider, and providesthis information to the appropriate entities to facilitate settlement.In this embodiment, the appropriate entities involve the Mobile NetworkOperator's accounts receivable 314 which is informed of the aggregateamount of sponsored data transferred during a billing period. The DSMPprovides corresponding usage information to the sponsored contentproviders account payable system 310. Thus, the content provider isinformed as to how much usage occurred for data provided to users of themobile network operator, and the mobile network operator is alsoinformed.

In another embodiment, the GGSN 308 can route sponsored data directed tothe sponsored content provider and then inform the DSMP of how much datawas transferred. However, it is generally easier for the DSMP todirectly handle the data traffic and determine how much data wastransferred

There are different mechanisms that can be used to distinguishconventional (non-sponsored) data from sponsored data. This distinctioncan be done by the mobile network operator, by incorporating differenttypes of information. Thus, multiple embodiments are possible forimplementing toll free data or sponsored data in a GSM network.

One embodiment involves using different Access Point Name (“APN”) valuesto distinguish between sponsored and non-sponsored data. In thisembodiment, the SGSN of the mobile network operator receives a requestfor data involving a particular APN value, and the SGSN then uses theAPN to select one of several GGSNs. Conceptually, different APN valuescan be mapped to the same or different GGSNs. In one embodiment, for anAPN value associated with sponsored data, the request is routed to alogically or physically dedicated GGSN that only handles sponsored data.The GGSN, in turn, routes the sponsored data to the DSMP.

The APN is essentially a data string representing an address that isresolved by a domain name server into a numerical address that providesrouting information for the SGSN and GGSN. The APN consists of twoparts: the Network ID which identifies the external service requested bythe subscriber, and the Operator ID which specifies routing information.The APN is used to determine a private address that is the IP address ofthe GGSN involved in providing the sponsored data connection. In somenetworks, different APN values can be used to identify physicallydifferent GGSNs implementing the sponsored and non-sponsored dataservices. In other embodiments, the different APN values are used toroute to a specified single physical GGSN, where the APN valueidentifies a logical or virtual GGSN implemented within the singledevice. In this embodiment of FIG. 3, the GGSN 308 is configured so thatit does not bill the wireless user for the session data (sponsoreddata), but would bill for conventional data sent to a conventionalcontent provider 119.

The APN approach can be used in a GPRS system. The system does not haveto be GSM, but could be a 4G or CDMA based system, or even a wirelinesystem provided it incorporates an APN.

Another embodiment is to use a portal proxy. In this approach, the website identifier (e.g., URI or Uniform Resource Identifier) is used todistinguish between web sites that provide sponsored data versusnon-sponsored data. Specifically, all sponsored data web sites are“behind” a proxy server, which is in the DSMP, so that the DSMP controlsaccess to the sponsored content sites. The functionality of the portalproxy can be combined with other functional processing for ensuring thecontent provider is properly billed. The portal proxy approach can beapplied to a number of architectures which use web site identifiers, andcan be readily applied to other data communication architectures,including CDMA wireless data, wireline DOCSIS, etc.

Access Point Name Approach

One embodiment for using different APNs to identify different GGSNs isillustrated in FIG. 4. This embodiment uses different physical GGSNs forpurposes of illustration, with GGSN #1 shown as being used for toll freedata, and GGSN #2 being used for conventional (non-sponsored) data.However, the different GGSNs could simply be different logical entitiesin a single GGSN. In this case, GGSN #1 408 a is associated with a firstAPN value (shown here as APN #1). Once the GGSN is identified, the GGSNexamines an APN user name in the received message (which may be, in oneembodiment, a “Create PDP Context Request” message). In FIG. 4, the APNuser name (APN#1), which is associated with a particular toll freecontent provider, is processed by the identified GGSN (GGSN #1). OtherAPN user names may be processed for other toll free content providers. Asecond GGSN #2 408 b is associated with a second APN value, shown as APN#2 for simplicity. GGSN #2 is used for conventional data traffic andprocesses APN user names associated with conventional traffic. The SGSNis responsible for interacting with the appropriate GGSN, by selectingthe appropriate GGSN based on the corresponding APN value. In actualembodiments, the APN value could be structured such as, e.g.,APN=Advertisername.mno123.mcc123.gprs.

The determination of which APN is used (and hence which GGSN is used) isdetermined by the initial request from the mobile station set. In oneembodiment, one of several browsers could be selected by a user. Thus, aparticular toll free browser could be used by a user to initiate therequest. An example can illustrate how this can occur. A browser ormobile application, is identified to the user as being associated with aparticular retailer, referred to as “Retailer.” The user downloads theRetailer's browser into their mobile phone. When the user is shopping inthe retailer's store, the user selects the Retailer mobile applicationused to provide toll free data access to selected sites. This browsercould be limited to certain toll free sites (e.g., hosted by theRetailer at its web-servers) or could be used to access any toll freesites recognized by the operator. A generic toll free application couldbe developed, or a business specific application could be defined.

GGSN#2 can be considered as the regular, normal GGSN used forconventional data transfer (a corresponding dotted line for conventionalsession data usage is not shown in FIG. 4). Usage of GGSN#2 results inthe session data usage charged to a user's account in a conventionalmanner. However, when GGSN#1 is used, the APN is indicative that thedata is sponsored data and conventional billing does not occur. Thus,GGSN#1 is configured to avoid billing the user for data sessionsreceived using the toll free APN value. While two distinct GGSNs areshown, these could easily be integrated into one GGSN.

Returning back to the case where a sponsored data request is made, therequest is sent via the BTS to the SGSN 306. The SGSN performs variousprerequisite functions as are known in the art. The SGSN then examinesthe APN address and routes the request to the appropriate GGSN.Specifically, sponsored data is routed to the sponsored data GGSN#1 408a, which then arranges establishment of a data session with the contentprovider. In this illustration, the GPRS Tunneling Protocol 403 (“GTP”)is established between the SGSN and GGSN #1. The dotted line 403illustrates the originating and terminating locations of the datatransferred. GGSN #1 is configured to measure the data transferred foreach particular subscriber, but it does not charge each subscriber forthe data transfer. In this embodiment, the GGSN #1 is further configuredto provide usage information to the DSMP (but not the session dataitself), which processes the usage data so that the toll free contentprovider is charged accordingly. Thus, in some embodiments the GGSN#1can be implemented by modifying a conventional GGSN thereby providingthe Data Session Management Platform of FIG. 2. However, these are shownas two separate entities for purposes of illustration in FIG. 4. Inanother embodiment, the GGSN #1 may direct the data of the data sessionitself to the DSMP, which in turn routes it using the Internet. In thiscase, the data usage can be determined by the DSMP as opposed to theGGSN.

As noted, traffic directed to APN #2 is processed by GGSN #2 and is usedto access data that is conventionally billed. Thus, different APN valuesare used to distinguish which GGSN handles the data, and thus determineswhether the data transferred is conventional data (e.g., included in thesubscriber's data usage plan) or whether it is sponsored content data(e.g., it is exempted from the subscriber's usage plan). The SSGN 306queries a domain name server to resolve the APN as to which GGSN shouldreceive the request and data.

In the embodiment shown in FIG. 4, once the GGSN establishes the datasession, the GGSN then informs the DSMP 312 in FIG. 4 of the usage data.The DSMP processes the data to generate the appropriate records, whichmay then transmit to the mobile network operator's (“MNO's”) accountreceivable systems 314 and the content provider's account payablesystems 413. Alternatively, the DSMP provides only reports to the MNOand the content provider (and/or sponsor). The accountspayable/receivable systems are systems operated by (or on behalf of) themobile network operator and content provider, and which track usageand/or the amounts due. The DSMP can provide reports to each entityindicating data session usage (on a detailed or aggregate basis), or canprovide a detailed invoice/amount due that indicates a dollar amount aswell as the data session usage information.

FIG. 5 illustrates a line diagram 500 involving some of the systemcomponents illustrated in FIG. 4 for accomplishing sponsored dataaccess. In FIG. 5, the mobile station (“MS”) transmits an “AttachRequest” message 502 to the SGSN for initiating data service. The SGSNresponds with an “Attach Response” message 504 accepting the request.The MS then is in a position to request establishment of the Packet DataProtocol (“PDP”) context by sending an “Activate PDP Context Request”message 506. The establishment of the PDP context requests establishmentof a GTP tunnel with the remote GGSN. The request includes the APNvalue, which in this case is presumed to be associated with toll freedata. The APN value has to be included in the request from the mobilestation and may include a programmed username and password value (notshown in FIG. 5). This can be used to ensure authorized access to thecontent. The mobile station would also typically include an identifier,such as its MSISDN or international mobile subscriber identifier(“IMSI”) value.

The SGSN in step 508 initiates a “DNS Query” to a domain name server toresolve the IP address of the GGSN associated with the APN, and afterthe “DNS Response” 510 is received, the SGSN then initiates a“Create_PDP_Context_Request” message 512. This request is made to theGGSN associated with the APN value. The GGSN may authentic the user,such as using the well known RADIUS procedures, which are well known inthe art. After completion, a “DHCP Address Request” message 516 and“DHCP Address Response” message 518 are sent. The GGSN can then confirmthe creation of the PDP context in the “Create_PDP_Context_Response”520, which results in the “Activate PDP Context Response” 522. At thispoint, the Mobile Station is able to transfer IP data in step 524 withthe sponsored content provider.

The GGSN illustrated in the embodiment of FIG. 4 is a modified versionof a conventional GGSN. While some of the functions performed by theDSMP (e.g., the modified conventional GGSN) are similar in scope to aGGSN, additional functions are performed by the DSMP to implement thesponsored data service. One difference is that the DSMP does not reportdata usage for determining a wireless user's data usage for billing in aconventional manner. Specifically, data usage is reported by the DSMPfor billing the content provider, not the wireless user. A conventionalGGSN creates records, sometimes called “call detail records” (“CDRs”)that records information about a call, or more accurately in this case,a data session. The CDR typically indicates how much data has beentransferred between the originating and terminating entities. However,as noted the DSMP processes usage data for generating a bill or usagereport to the content provider. These records can be in the form of aCDR. Further, the DSMP may incorporate financial and settlementfunctions for settling payment with the content provider. In otherembodiments, the DSMP may send usage data to a separate system forperforming this function.

As noted previously, in other embodiments the DSMP 312 functionality ofFIG. 4 may be incorporated into the GGSN#1 408 a, so that thesefunctions are implemented in a single physical entity.

Portal Proxy Approach

A second approach for accomplishing access to sponsored data involvesusing a proxy server to handle requests from the mobile user. Thisapproach is based on the mobile device requesting sponsored data whichinvolves using a proxy server that is functionally present in the DSMP.In one embodiment, a specially configured mobile application in thehandset is used to formulate the sponsored data request to the DSMP.Based on the indicated web site request generated by the mobile device(as opposed to an APN value), the request is processed by the GPRSsystem of the mobile operator. For non-GSM based systems, othercorresponding elements may be involved. If the request is for accessinga web site of a sponsored content provider, the GPRS system then routesthe request to the DSMP and the GPRS system avoids billing the user'saccount for data usage. Next, a proxy server function in the DSMPdetermines the sponsored content provider and routes the requestaccordingly. If the request is for accessing a conventional,non-sponsored web site, then GPRS will instead forward the request tothe Internet, and on to the conventional content provider's web site. Inthe case of conventional, non-sponsored data, existing billingprocedures can be incorporated.

One embodiment of the architecture and message flow is shown in FIG. 6.It is useful to compare how conventional (non-sponsored) message flow isprocessed compared to sponsored data. The mobile user 100 initiates arequest which is processed by the GPRS system 602. If the request is fora conventional content provider, the GPRS system is configured toanalyze the requested URI, and if the URI is associated with aconventional content provider, the GPRS then forwards the request over afacility to the Internet 104, which in turn routes the request to thecontent provider 606. The GPRS also bills for data usage in aconventional manner. Typically, such usage is billed by the mobilenetwork operator consistent with the user's rate plan. If, however, theGPRS determines that the destination is a sponsored content providerbased on resolving the domain name identified in the request, the GPRS602 forwards the request to the DSMP 604. In this case, the GRPS isconfigured to not bill the user.

The DSMP 604, in turn receives the request from the GPRS system, andinitiates various procedures for recording usage aspects (if not alreadyinitiated for that session), and resolves the address of the destinationdomain name, which is the address of the particular sponsored contentprovider. The path of the data request is shown by the dotted line 612of FIG. 6 which originates with the mobile user, is routed to the GPRSsystem, on to the DSMP, then to the Internet, and finally to the contentprovider. Response data from the content provider would occur in thereverse direction.

The aforementioned request messages can be formatted as a GET message.For a sponsored data request, the request could be formatted as follows:GET:/Content_Provider1.com/index.html. In this embodiment, the parameter“Content_Provider1.com” is the domain name of the sponsored contentprovider 608. This domain name is resolved by a proxy server function inthe DSMP. Prior to this, the GPRS system resolves the domain nameDSMP_name.com to identify the DSMP. If the non-sponsored contentprovider 606 was intended to be addressed, then e.g.,“content_provider2.com” would have been indicated in the original GETmessage. Further, the domain name “DSMP_name.com” would not be present.Obviously, there can be a plurality of sponsored and non-sponsoredproviders associated with a corresponding plurality of domain names, butonly one of each is shown in FIG. 6.

In the GET message, the domain name DSMP_name.com is used by the GRPSsystem to identify the DSMP, which in this embodiment is used to routesponsored traffic requests to the DSMP. Thus, in this embodiment, theGPRS is the point at which non-sponsored data is segregated fromsponsored data.

Once the DSMP receives the request, the DSMP 604 records informationrelated to the session, such as the length of the data session or theamount of data transferred from the sponsor's site. The DSMP typicallyalso performs various other functions associated with toll free datarequests, such as checking the status of the toll free campaign withrespect to the request. The DSMP is aware of all data passing through itand is aware of how long or how much data was transferred. Theconnectivity between the DSMP and content provider can be provided indifferent ways, including through a virtual private network connectionto the appropriate content provider. Similarly, the connectivity betweenthe GPRS and the DSMP can occur in different ways. In this embodiment,the DSMP appears to the mobile network operator as an IP address withinthe mobile network operator's GRX or IPX network. In other embodiments,the DSMP may be an IP addressable element outside the mobile networkoperator's network connected via private facilities, or the Internet. Inother embodiments, the DSMP may be integrated within the GPRS system, ora stand-alone system as is shown in FIG. 6.

Processing of Session Establishment Rules

The DSMP is involved when a sponsored data session is initiated. Incertain circumstances, a request for a sponsored data session mayoriginate from a user where the request is incompatible with thecampaign rules established for that sponsored content provider. Forexample, the availability of sponsored data may be associated with anadvertising campaign having specified starting/ending dates. Theavailability of sponsored data may be advertised to a wireless user byplacing a placard near a product in a retail store indicating that“free” data transfer is available for the time period. If the storepersonnel do not timely remove the placard after the ending date of thecampaign, wireless users may nevertheless attempt to access thesponsored content provider. Alternatively, the advertising campaign mayinvolve printed ads, and the wireless user obtains an obsolete copy ofthe printed ad and attempts to access the web site after the campaignhas ended. For whatever reason, users may attempt to initiate asponsored data session after the sponsored data campaign has ended andin such cases, the user should not be able to access the data on a tollfree basis and the content provider should not be billed. Thus, the DSMPmay perform various rule-checking procedures associated with therequest. Performance of this function is facilitated by the embodimentswhere the data session is routed through the DSMP. The DSMP can act as a“gatekeeper” to ensure that only valid toll free data sessions areestablished through it.

Checking the campaign rules can limit access to the content providerbased on date, time, originating mobile network provider, MSISDN of thewireless user, or other parameters available to the DSMP when therequest is made for a toll free session. The DSMP is aware of the timeof the request and can compare this with the campaign limits establishedfor that content provider. The DSMP may also be aware of the particularwireless user (via MSISDN, if provided) and can perform various othertypes of rule checking. For example, a wireless user reporting a stolenphone or an account which has been compromised can have the accountidentified via MSISDN. At the beginning of each session, the DSMP couldcheck whether the MSISDN is authorized or is indicated on a “black list”(or “negative list”) of prohibited users. Alternatively, a user abusingthe sponsored content service could be barred from accessing content ofa specific content provider, or otherwise barred entirely from accessingany sponsored data content provider.

In other embodiments, a “positive list” of users authorized to accessthe sponsored data can be created. It is possible to define a list ofauthorized users for a particular content provider. For example, thelist could be defined by the content provider as including the contentprovider's employees, customers, premium customers, etc. In otherinstances, the sponsored data may be accessed only by one of: pre-paidwireless users, post-paid wireless users, post-paid customers in goodstanding and having a certain service level with the service provider orhaving a certain demographic, etc.

The sponsor may also desire to limit access to sponsored content bydefining various sponsor defined limitations. Typically, the contentprovider will indicate a beginning and ending date of the campaign, butthere may also be other limitations defined, including a maximum numberof accesses or “hits” to the sponsored content, a limit on the totalnumber of bytes of data transferred, minutes of use, a total monetaryliability for sponsored data access, etc. Those skilled in the art willrecognize that various types of authorization and security processingcan occur prior to allowing the wireless user access to the sponsoreddata content.

If access by a wireless user is denied, an appropriate notificationmessage can be sent to the wireless user. This message can be initiatedby the DSMP (if the DSMP is involved with establishment of the session)or the DSMP can notify an appropriate component in the mobile networkoperator (e.g., the SSGN or GGSN). In other embodiments, the contentprovider could initiate this message. Further, if any one of the accesslimitations is reached during an active session, the system can notifythe user of such conditions. For example, if a time limit has beenexceeded for a sponsored content session, the user may be informed ofsuch condition. Information could be displayed on the mobile stationindicating that continuing access to the data will be charged at theprevailing rates to the wireless user as defined by the serviceprovider. Similarly, if the user migrates away (e.g., accesses adifferent web site) from a sponsored content provider, a notificationmay be sent informing the user that conventional data plan rates will beapplied. Typically, the notification is sent to the user from the DSMP.

Usage Data Clearing Process Flow

The usage data clearing process flow refers processing usage data forpurposes of reconciling the accounts associated with a user accessingsponsored content. Proper reconciliation of accounts include: 1)suppressing the billing of the wireless user for accessing the sponsoreddata, and 2) processing data so that the sponsor is properly billedand/or other parties properly reimbursed. The suppression of billing awireless user occurs simply by not generating the call detail recordsthat are normally used to bill the wireless user. Thus, this ischaracterized by the absence of processing specific to a user's account.Those skilled in the art will recognize that in various embodiments,various mechanisms can be used to avoid the generation of the wirelessusers' call detail record or billing record. For example, in oneembodiment the GGSN handling the sponsored data is programmed to notbill the user; in other embodiments, the GGSN could generate usagerecords which are then deleted or otherwise ignored.

For the APN approach, the processing in the DSMP is shown in FIG. 7.Recall that in the APN approach, the SGSN creates a GTP tunnel directlywith the modified GGSN (the DSMP), therefore bypassing the conventionalGGSN normally used. Since the conventional GGSN is bypassed, no billingrecords are generated for the wireless user. Instead, the DSMP generatesrecords directed to inform the content provider and/or mobile operatorof the data usage. In some embodiments, the usage data is combined withan amount due to create a bill for the content provider.

In FIG. 7, the process begins in step 711 with the establishment of thesponsored data session. In this case, the conventional GGSN is bypassedand the mobile operator does not generate a conventional Call DetailRecord (“CDR”) for the wireless user.

In the next step, step 712, the modified GGSN (which functions in thisembodiment as the DSMP), generates a modified GGSN CDR (“G-CDR”), whichreflects the sponsored data session initiated by the wireless user, asidentified by the MSISDN (mobile station telephone number). (In otherembodiments, the DSMP may generate the CDR record.) Step 713 shows thatthe CDR record reflects the mobile network operator as the source (whichcan be derived from various sources, including the APN, username, and/orpassword in the initial request) and also notes the destination contentprovider. The size of the session, which can be measured in time, data,or other parameter, is also noted. The CDR records may be created at thebeginning of a session and are usually completed at the end of thesession.

The DSMP in step 714 looks up an identifier associated with the contentprovider (“content provider identifier”). This could be a pseudo PrivateMobile Network code (PMN) associated with the content provider oranother type of identifier, such as an identifier allocated byTransferred Account Data Interchange Group (“TADIG”). In one embodiment,in step 715, the record format is converted from a CDR format to aTransferred Account Procedure (“TAP”) formatted record or some otherformatted record (e.g., a Cellular Inter-carrier Billing Exchange Recordor “CIBER”). A number of standard based formats can be used, and in oneembodiment, a GSM standard referred to as Temporary Document 57 (“TD57”) can be used. This is also known as “TAP 3,” which is a billingformat used by roaming service providers for transmitting billingrecords to the home network operator. In other embodiments, proprietaryor non-standardized formats could be used for conveying billinginformation. In further embodiments, the usage reports can be sentwithout converting them into another format. In step 716, the DSMP sendsa TAP file to a clearinghouse, which is a third party entity forreconciling data and/or financial records. In step 717, theclearinghouse receives the file and creates the appropriate accountsreceivable and payable reports.

Upon receiving the report, the content provider in step 718 is in aposition to know how much to pay for the sponsored data (shown here asan amount due of $2.00). Similarly, in step 719, the mobile operatorreflects a corresponding amount in its accounts receivable that is due.In one embodiment, the content provider in step 720 periodically paysthe DSMP provider, and the DSMP provider then pays the mobile networkoperator in step 721. As noted, there are alternative embodiments, suchas where the content provider could pay the mobile network operatordirectly, bypassing the DSMP. In such embodiments, the records from theDSMP may still be used to reconcile the amounts due. In otherembodiments, a different third party may be involved.

FIG. 8 shows a similar process that may be used if the portal proxyapproach is used. Recall that in the portal proxy approach, the domainname is indicative of whether sponsored data processing is applicable ornot. Consequently, in step 801, if the mobile operator receives arequest indicating a URI with a sponsored content destination (e.g., anaddress indicating “proxy.com/cp”) then the mobile operator suppressesconventional billing for data to/from the domain, e.g., “proxy.com.” Themobile operator passes the request including the MSISDN (mobiletelephone number) to the DSMP. In other embodiments, the mobile networkoperator may provide a unique ID for the end-user, as opposed to aMSISDN value.

In step 802, the DSMP (which may be integrated or in communication withthe proxy server) notes the creation of a sponsored data sessioninvolving the end user. The DSMP may record the volume of data, theduration, a combination thereof, or other aspects of the session forpurposes of generating usage data used to charge the content provider.The DSMP in step 803 then creates a record of the session in an XML TAPfile format. The record is formatted in step 804 such that the source isidentified as the mobile network operator indicating the request fromstep 801. The destination is set as the content provider (“CP”) who issponsoring the data, and other parameters are recorded, such as the typeof call (“GPRS”) and session size (time or data volume).

In step 805, the DSMP determines an identifier, such as the pseudoPrivate Mobile Network (“PMN”) code associated with the contentprovider. Typically, a look-up table in the memory of the DSMP maintainsan association of the content provider and a pseudo PMN assigned to thatcontent provider. The pseudo PMN code was assigned previously, duringthe contractual establishment of the sponsored data campaign. The pseudoPMN code allows the DSMP to treat the content provider similar as a PMNprovider for data clearing purposes. However, the content provider neednot actually have, or provide, a private mobile network. As notedpreviously, a TADIG code or other sponsor identifier may be used in lieuof a pseudo PMN code.

In step 806, the DSMP may convert the call detail record to a GSMstandard based TD.57 compliant TAP record. Not all embodiments requirereformatting the usage record information into another format. In otherembodiments, the function of converting usage information into anotherformat, which can be a standardized or non-standardized format, may becarried out by a separate system from the DSMP. In step 807, this TAPrecord is then transmitted using conventional communication facilitiesto an appropriate clearinghouse system (“CHS”). The records can be sentin real time as they are generated, at the end of each day, monthly, oraccording to some other periodic basis. In step 808 the clearinghouse(which may be integrated with the DSMP system) creates financial reportsthat form the basis for payable amount and the corresponding receivableamount based on the records generated.

For example, in step 809, information regarding the amount due isprovided to the content provider such that the content provider recordsan amount payable in their systems (the amount shown here, for purposesof illustration, as $2.00). Corresponding information is provided to themobile operator reflecting that a receivable of $2.00 is due from thecontent provider.

In this embodiment, in steps 811 and 821, the content provider pays,directly or indirectly, the mobile operator. At this point, there are anumber of billing and settlement arrangements that are possible. Forexample, in this embodiment, the DSMP acts to settle the financialamount between the content provider and the mobile operator. In otherembodiments, the content provider and mobile operator may reconciledirectly with each other, based on reports from the DSMP. For example,the mobile operator could invoice the content provider based on the DSMPusage reports. In other embodiments, a third party clearinghouse may beinvolved in settling the transaction. Regardless of the arrangement, theDSMP is the entity that generates the data from which reconciliation isbased. It is possible that the content provider may further recordaspects associated with the session so that verification of the DSMPvalues is possible.

In various embodiments, various records and/or files can be transmittedto the mobile network operator and/or the content provider at theinitiation of the DSMP or the clearinghouse. This can be analogized to a“push” data transfer. However, in other embodiments, the contentprovider and/or mobile network operator can “pull” the data. Forexample, the MNO can determine when the data will be requested. This canbe accomplished by the DSMP or clearinghouse making the appropriate datausage information available at a web site or portal, which is thenaccessed by the content provider and/or MNO at its convenience. Variouswell known techniques known in the art for requesting or transferringthe usage information can be used.

One embodiment of the DSMP system described previously is shown in FIG.9. In FIG. 9, the DSMP system comprises a processor 901. The processorinterfaces via an input/output bus 909 to an I/O controller 911. The I/Ocontroller may interface with other system components via interface 915as required. The other components that DSMP system may interface mayinclude the SGSN or GGSN of the mobile operator, content provider,accounting systems, etc. The processor also communicates via a data bus905 with a memory system 907, which comprises various forms of computerreadable media, including primary memory 902, such as RAM, forms ofpermanent primary memory such as ROM, FLASH memory, etc. 903, andsecondary storage, such as disk storage 904. Other variations and typesof memory storage technology can be used. The memory typically storesthe programming steps which when executed by the processor causes thesystem to perform the processing previously described. In otherembodiments, different processing configurations and arrangements can beused, including distributed processing, parallel processing,client-server type arrangements, specialized purpose processorsprogrammed accordingly, etc. The system shown in FIG. 9 could also beembodied as a general purpose computer programmed to perform the stepsto accomplish the invention. Those skilled in the art will recognizethat the principles of the present invention can be applied in a numberof ways.

The above illustrates several embodiments of the toll free service andassociated architecture. Variations in the architecture, messaging, andprocedures are possible and one skilled in the art could use theinformation presented herein to develop other embodiments not describedherein.

That which is claimed:
 1. A method comprising: receiving a request viaan apparatus from a mobile network operator serving a wireless user, therequest is for sponsored data from a network device of a contentprovider, the request comprising an identification of the sponsored datain the network device; detecting, via the apparatus, a sponsored datacampaign end date in the request and that the sponsored data campaignend date has not occurred; enabling provision of a generated secondrequest, via the apparatus, to the network device requesting thesponsored data; receiving, via the apparatus, the sponsored data fromthe network device; enabling provision, via the apparatus, of thesponsored data to a wireless user; and generating, via the apparatus, ausage record for charging the content provider for providing thesponsored data.
 2. The method of claim 1 wherein the request comprises aGlobal System for Mobile Communications (GSM) based Access Point Name(APN) indicating a Gateway GSM Packetized Radio Services (GPRS) SupportNode (GGSN) of the network operator connected to an interface of theapparatus.
 3. The method of claim 2 wherein the usage record indicates awireless user identifier associated with the wireless user, a mobilenetwork operator identifier associated with the network operator, and atleast one of a time duration of the sponsored data transfer or a volumeof the sponsored data transfer.
 4. The method of claim 3 wherein saidusage record further comprise a monetary amount associated with thesponsored data provided to the wireless user, and the apparatus isconfigured to transfer the usage record to the content provider.
 5. Themethod of claim 4, further comprising: determining, via the apparatus acontent provider identifier associated with the content provider from atable stored in memory of the apparatus; and indicating, via theapparatus, the content provider identifier in the usage record.
 6. Themethod of claim 3: transferring, via the apparatus, the usage record tothe mobile network operator.
 7. The method of claim 1 wherein therequest comprises a Uniform Resource Identifier (URI) and wherein themethod further comprises: determining from the URI the sponsored datacampaign end date.
 8. The method of claim 7 wherein the usage recordindicates a wireless user identifier associated with the wireless user,a mobile network operator identifier associated with the mobile networkoperator, and at least one of a time duration of the sponsored datatransfer or a volume of the sponsored data transfer.
 9. The method ofclaim 8 wherein the usage record further comprises a monetary amountassociated with the sponsored data provided to the wireless user andwherein the method further comprises: transmitting, via the apparatus,the usage record to the content provider.
 10. The method of claim 9wherein the apparatus comprises a Data Session Management Platform(DSMP) and wherein the method further comprises: transmitting, via theapparatus, the usage record to the mobile network operator.
 11. Anapparatus comprising: at least one processor; and at least one memoryincluding computer program code, the at least one memory and thecomputer program code configured to, with the at least one processor,cause the apparatus to perform at least the following: receive a requestfor sponsored data transfer from a mobile network operator serving awireless user, the request identifying a network device of a contentprovider offering the sponsored data; determine from the request asponsored data campaign data parameter comprising a sponsored datacampaign end date that has not yet occurred; enable provision of agenerated a second request to the network device for the sponsored data;receive the sponsored data from the network device; enable provision ofthe sponsored data to the wireless user; and generate a usage record forcharging the content provider for providing the sponsored data.
 12. Theapparatus of claim 11, wherein the at least one memory and the computerprogram code are further configured to, with the at least one processor,cause the apparatus to: store the usage record in the memory; andtransmit the usage record to the mobile network operator.
 13. Theapparatus of claim 12 wherein the usage record comprises a wireless useridentifier associated with the wireless user, a mobile network operatoridentifier associated with the mobile network operator, and at least oneof a time duration of the sponsored data transfer, a volume of thesponsored data transfer, or a monetary amount associated with thesponsored data provided to the wireless user.
 14. The apparatus of claim13, wherein the request comprises a Global System for MobileCommunications (GSM) based Access Point Name (APN) and wherein the atleast one memory and the computer program code are further configuredto, with the at least one processor, cause the apparatus to: determinethe sponsored data campaign data parameter comprising the sponsored datacampaign end date using the APN to ascertain the sponsored data campaigndata parameter from a plurality of sponsored data campaign dataparameters.
 15. The apparatus of claim 13, wherein the request comprisesa Uniform Resource Identifier (URI) and wherein the at least one memoryand the computer program code are further configured to, with the atleast one processor, cause the apparatus to: determine the sponsoreddata campaign data parameter comprising the sponsored data campaign enddate using the URI to ascertain the sponsored data campaign dataparameter from a plurality of sponsored data campaign data parameters.16. The apparatus of claim 13, wherein the usage record furthercomprises a content provider identifier associated with the request andwherein the at least one memory and the computer program code arefurther configured to, with the at least one processor, cause theapparatus to: transmit the usage record to the content provider.
 17. Theapparatus of claim 13, wherein the at least one memory and the computerprogram code are further configured to, with the at least one processor,cause the apparatus to: reformat the usage record prior to transmittingthe usage record to the mobile network operator.
 18. The apparatus ofclaim 11, wherein the at least one memory and the computer program codeare further configured to, with the at least one processor, cause theapparatus to: store a plurality of usage records in a file, wherein eachrecord is associated with the content provider and a respective one of aplurality of wireless users.
 19. The apparatus of claim 18, wherein theapparatus comprises a Data Session Management Platform (DSMP) andwherein the at least one memory and the computer program code arefurther configured to, with the at least one processor, cause theapparatus to: transfer the plurality of usage records to the mobilenetwork operator and the content provider.
 20. A computer programproduct comprising at least one non-transitory computer-readable storagemedium having computer-readable program code portions stored therein,the computer-readable program code portions comprising: program codeinstructions configured to facilitate receipt, via an apparatus, of arequest for sponsored data transfer from a mobile network operatorserving a wireless user, the request identifying a network device of acontent provider offering the sponsored data; program code instructionsconfigured to determine from the request a sponsored data campaign dataparameter comprising a sponsored data campaign end date that has not yetoccurred; program code instructions configured to enable provision, viathe apparatus, of a generated second request to the network device forthe sponsored data; program code instructions configured to facilitatereceipt, via the apparatus, of the sponsored data from the networkdevice; program code instructions configured to enable provision, viathe apparatus, of the sponsored data to the wireless user; and programcode instructions configured to generate, via the apparatus, a usagerecord for charging the content provider for providing the sponsoreddata.
 21. The computer program product of claim 20, further comprising:program code instructions configured to enable storing of the usagerecord in the medium; and program code instructions configured to enabletransmission of the usage record to the mobile network operator.
 22. Thecomputer program product of claim 21 wherein the usage record comprisesa wireless user identifier associated with the wireless user, a mobilenetwork operator identifier associated with the mobile network operator,and at least one of a time duration of the sponsored data transfer, avolume of the sponsored data transfer, or a monetary amount associatedwith the sponsored data provided to the wireless user.
 23. The computerprogram product of claim 22, wherein the request comprises a GlobalSystem for Mobile Communications (GSM) based Access Point Name (APN) andwherein the computer program product further comprises: program codeinstructions configured to determine the sponsored data campaign dataparameter comprising the sponsored data campaign end date using the APNto ascertain the sponsored data campaign data parameter from a pluralityof sponsored data campaign data parameters.
 24. The computer programproduct of claim 22, wherein the request comprises a Uniform ResourceIdentifier (URI) and wherein computer program product further comprises:program code instructions configured to determine the sponsored datacampaign data parameter comprising the sponsored data campaign end dateusing the URI to ascertain the sponsored data campaign data parameterfrom a plurality of sponsored data campaign data parameters.
 25. Thecomputer program product of claim 22, wherein the usage record furthercomprises a content provider identifier associated with the request andwherein the computer program product further comprises: program codeinstructions configured to enable transmission of the usage record tothe content provider.
 26. The computer program product of claim 22,further comprising: program code instructions configured to reformat theusage record prior to transmitting the usage record to the mobilenetwork operator.
 27. The computer program product of claim 20, furthercomprising: program code instructions configured to store a plurality ofusage records in a file, wherein each record is associated with thecontent provider and a respective one of a plurality of wireless users.28. The computer program product of claim 27, wherein the apparatuscomprises a Data Session Management Platform (DSMP) and wherein thecomputer program product further comprises: program code instructionsconfigured to transfer the plurality of usage records to the mobilenetwork operator and the content provider.
 29. An apparatus for denyingtransfer of data requested for transfer by a wireless user, theapparatus comprising: at least one processor; and at least one memoryincluding computer program code, the at least one memory and thecomputer program code configured to, with the at least one processor,cause the apparatus to perform at least the following: receive a requestfrom a mobile network operator, the request originating from a wirelessuser requesting transfer of data between a mobile phone and a sponsoredcontent provider, wherein the apparatus communicates with a mobilenetwork operator serving the mobile phone, wherein the request comprisesdata utilized to identify the sponsored content provider; retrieve a setof sponsored data campaign parameters associated with the request storedin the memory, wherein the set of sponsored data campaign parameterscomprises a campaign end date for transfer of the sponsored data fromthe sponsored content provider; determine the end date has occurred; notforwarding the request to the sponsored content provider; generate amessage to the wireless user indicating the sponsored data isunavailable; and generate a record stored in the memory reflectingreceipt of the request.
 30. The apparatus of claim 29 wherein therequest comprises a Global System for Mobile Communications (GSM) basedAccess Point Name (APN) username, and wherein the at least one memoryand the computer program code are configured to, with the at least oneprocessor, cause the apparatus to: retrieve the set of sponsored datacampaign parameters using the APN username.
 31. The apparatus of claim20 wherein the request comprises a Uniform Resource Identifier (URI) andwherein the at least one memory and the computer program code areconfigured to, with the at least one processor, cause the apparatus to:retrieve the set of sponsored data campaign parameters using an AccessPoint Name (APN) username.